Scheduling broadcast or multicast communications for new radio

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a broadcast or a multicast (broadcast/multicast) scheduling configuration for a physical downlink control channel (PDCCH), the broadcast/multicast scheduling configuration identifying, for receiving broadcast/multicast communications, at least one of: a plurality of radio network temporary identifiers that are respectively associated with a plurality of beams, or one or more bandwidth parts. The UE may receive a broadcast/multicast communication associated with a broadcast/multicast control channel or a broadcast/multicast traffic channel via a physical downlink shared channel in accordance with the broadcast/multicast scheduling configuration for the PDCCH. Numerous other aspects are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/947,031, filed on Jul. 15, 2020, entitled “SCHEDULING BROADCAST ORMULTICAST COMMUNICATIONS FOR NEW RADIO” (now U.S. Pat. No. 11,395,260),which claims priority to U.S. Provisional Patent Application No.62/882,257, filed on Aug. 2, 2019, entitled “SCHEDULING BROADCAST ORMULTICAST COMMUNICATIONS FOR NEW RADIO” the contents of which areincorporated herein in their entirety.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and to techniques and apparatuses for schedulingbroadcast or multicast communications for New Radio.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (for example,bandwidth, transmit power, or the like, or a combination thereof).Examples of such multiple-access technologies include code divisionmultiple access (CDMA) systems, time division multiple access (TDMA)systems, frequency-division multiple access (FDMA) systems, orthogonalfrequency-division multiple access (OFDMA) systems, single-carrierfrequency-division multiple access (SC-FDMA) systems, time divisionsynchronous code division multiple access (TD-SCDMA) systems, and LongTerm Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to theUniversal Mobile Telecommunications System (UMTS) mobile standardpromulgated by the Third Generation Partnership Project (3GPP).

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment (UEs) to communicate on a municipal, national,regional, and even global level. New Radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the 3GPP. NR is designed to better support mobilebroadband Internet access by improving spectral efficiency, loweringcosts, improving services, making use of new spectrum, and betterintegrating with other open standards using orthogonal frequencydivision multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on thedownlink (DL), using CP-OFDM or SC-FDM (for example, also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL),as well as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. However, as the demand formobile broadband access continues to increase, there exists a need forfurther improvements in LTE and NR technologies. Preferably, theseimprovements are applicable to other multiple access technologies andthe telecommunication standards that employ these technologies.

In some cases, wireless networks may support broadcast communication, inwhich a communication is provided to all UEs of a cell, or multicastcommunication, in which a communication is provided to a group of UEs.Broadcast or multicast (broadcast/multicast) communications may beuseful for broad dissemination of information, such as emergency alerts,audio content, or video content. However, there may not be mechanismsfor scheduling broadcast/multicast communications from multiple cells orusing multiple beams. Moreover, there may not be mechanisms forretransmission of broadcast/multicast communications to particular UEswhen broadcast/multicast traffic is multiplexed with unicast traffic.

SUMMARY

In some aspects, a method of wireless communication, performed by a userequipment (UE), may include receiving a broadcast or a multicast(broadcast/multicast) scheduling configuration for a physical downlinkcontrol channel (PDCCH), the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of radio network temporaryidentifiers (RNTIs) that are respectively associated with a plurality ofbeams, or one or more bandwidth parts (BWPs); and receiving abroadcast/multicast communication associated with a broadcast/multicastcontrol channel (MCCH) or a broadcast/multicast traffic channel (MTCH)via a physical downlink shared channel (PDSCH) in accordance with thebroadcast/multicast scheduling configuration for the PDCCH.

In some aspects, a method of wireless communication, performed by a basestation, may include transmitting, to a plurality of UEs, abroadcast/multicast scheduling configuration for a PDCCH, thebroadcast/multicast scheduling configuration identifying, for receivingbroadcast/multicast communications, at least one of: a plurality ofRNTIs that are respectively associated with a plurality of beams, or oneor more BWPs; and transmitting, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH.

In some aspects, a UE for wireless communication may include memory andone or more processors operatively coupled to the memory. The memory andthe one or more processors may be configured to receive abroadcast/multicast scheduling configuration for a PDCCH, thebroadcast/multicast scheduling configuration identifying, for receivingbroadcast/multicast communications, at least one of: a plurality ofRNTIs that are respectively associated with a plurality of beams, or oneor more BWPs; and receive a broadcast/multicast communication associatedwith an MCCH or an MTCH via a PDSCH in accordance with thebroadcast/multicast scheduling configuration for the PDCCH.

In some aspects, a base station for wireless communication may includememory and one or more processors operatively coupled to the memory. Thememory and the one or more processors may be configured to transmit, toa plurality of UEs, a broadcast/multicast scheduling configuration for aPDCCH, the broadcast/multicast scheduling configuration identifying, forreceiving broadcast/multicast communications, at least one of: aplurality of RNTIs that are respectively associated with a plurality ofbeams, or one or more BWPs; and transmit, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a UE, may causethe one or more processors to receive a broadcast/multicast schedulingconfiguration for a PDCCH, the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or more BWPs;and receive a broadcast/multicast communication associated with an MCCHor an MTCH via a PDSCH in accordance with the broadcast/multicastscheduling configuration for the PDCCH.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a base station,may cause the one or more processors to transmit, to a plurality of UEs,a broadcast/multicast scheduling configuration for a PDCCH, thebroadcast/multicast scheduling configuration identifying, for receivingbroadcast/multicast communications, at least one of: a plurality ofRNTIs that are respectively associated with a plurality of beams, or oneor more BWPs; and transmit, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH.

In some aspects, an apparatus for wireless communication may includemeans for receiving a broadcast/multicast scheduling configuration for aPDCCH, the broadcast/multicast scheduling configuration identifying, forreceiving broadcast/multicast communications, at least one of: aplurality of RNTIs that are respectively associated with a plurality ofbeams, or one or more BWPs; and means for receiving abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH.

In some aspects, an apparatus for wireless communication may includemeans for transmitting, to a plurality of UEs, a broadcast/multicastscheduling configuration for a PDCCH, the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or more BWPs;and means for transmitting, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, or processing system assubstantially described with reference to and as illustrated by thedrawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples in accordance with the disclosure in order thatthe detailed description that follows may be better understood.Additional features and advantages will be described hereinafter. Theconception and specific examples disclosed may be readily utilized as abasis for modifying or designing other structures for carrying out thesame purposes of the present disclosure. Such equivalent constructionsdo not depart from the scope of the appended claims. Characteristics ofthe concepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only some typical aspects of this disclosure and aretherefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a block diagram illustrating an example wireless network inaccordance with various aspects of the present disclosure.

FIG. 2 is a block diagram illustrating an example base station (BS) incommunication with a user equipment (UE) in a wireless network inaccordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of scheduling broadcast ormulticast communications in accordance with various aspects of thepresent disclosure.

FIG. 4 is a diagram illustrating an example process performed by a UE inaccordance with various aspects of the present disclosure.

FIG. 5 is a diagram illustrating an example process performed by a basestation in accordance with various aspects of the present disclosure.

FIGS. 6 and 7 are block diagrams of example apparatuses for wirelesscommunication in accordance with various aspects of the presentdisclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and are not to be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art may appreciate that the scope ofthe disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any quantity of theaspects set forth herein. In addition, the scope of the disclosure isintended to cover such an apparatus or method which is practiced usingother structure, functionality, or structure and functionality inaddition to or other than the various aspects of the disclosure setforth herein. Any aspect of the disclosure disclosed herein may beembodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like, orcombinations thereof (collectively referred to as “elements”). Theseelements may be implemented using hardware, software, or combinationsthereof. Whether such elements are implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system.

It should be noted that while aspects may be described herein usingterminology commonly associated with 3G or 4G wireless technologies,aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

Some wireless networks may support broadcast or multicast(broadcast/multicast) communication, which may be useful for broaddissemination of information, such as emergency alerts, audio content,or video content. However, there may not be mechanisms for schedulingbroadcast/multicast communications from multiple cells or using multiplebeams. Moreover, there may not be mechanisms for retransmission ofbroadcast/multicast communications to a particular user equipment (UE)when broadcast/multicast traffic is multiplexed with unicast traffic.

Some techniques and apparatuses described herein facilitate schedulingbroadcast/multicast communications. For example, a schedulingconfiguration for broadcast/multicast communications may define aplurality of radio network temporary identifiers (RNTIs) for abroadcast/multicast service (for example, for broadcast/multicastcommunications), each of which are mapped to a particular beam, toenable a UE to receive broadcast/multicast communications using multiplebeams. As another example, the scheduling configuration may define amapping of unicast hybrid automatic repeat request (HARQ) processidentifiers to multicast HARQ process identifiers to enableretransmission of a broadcast/multicast communication to a particularUE. In addition, some techniques and apparatuses described hereinfacilitate scheduling broadcast/multicast communications from multiplecells (for example, multiple cells of a single frequency network (SFN)).In this way, performance, reliability, and efficiency ofbroadcast/multicast communications may be improved.

FIG. 1 is a block diagram illustrating an example wireless network inaccordance with various aspects of the present disclosure. The wirelessnetwork may be a Long Term Evolution (LTE) network or some otherwireless network, such as a 5G or NR network. The wireless network mayinclude a quantity of base stations (BSs) 110 (shown as BS 110 a, BS 110b, BS 110 c, and BS 110 d) and other network entities. A BS is an entitythat communicates with UE(s) and may also be referred to as a Node B, aneNodeB, an eNB, a gNB, a NR BS, a 5G node B (NB), an access point (AP),a transmit receive point (TRP), or the like, or combinations thereof(these terms are used interchangeably herein). Each BS may providecommunication coverage for a particular geographic area. In 3GPP, theterm “cell” can refer to a coverage area of a BS or a BS subsystemserving this coverage area, depending on the context in which the termis used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, or another type of cell. A macro cell may cover a relativelylarge geographic area (for example, several kilometers in radius) andmay allow unrestricted access by UEs with service subscription. A picocell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (for example, a home) and mayallow restricted access by UEs having association with the femto cell(for example, UEs in a closed subscriber group (CSG)). A BS for a macrocell may be referred to as a macro BS. A BS for a pico cell may bereferred to as a pico BS. A BS for a femto cell may be referred to as afemto BS or a home BS. A BS may support one or multiple (for example,three) cells.

The wireless network may be a heterogeneous network that includes BSs ofdifferent types, for example, macro BSs, pico BSs, femto BSs, relay BSs,or the like, or combinations thereof. These different types of BSs mayhave different transmit power levels, different coverage areas, anddifferent impacts on interference in the wireless network. For example,macro BSs may have a high transmit power level (for example, 5 to 40Watts) whereas pico BSs, femto BSs, and relay BSs may have lowertransmit power levels (for example, 0.1 to 2 Watts). In the exampleshown in FIG. 1, a BS 110 a may be a macro BS for a macro cell 102 a, aBS 110 b may be a pico BS for a pico cell 102 b, and a BS 110 c may be afemto BS for a femto cell 102 c. A network controller 130 may couple tothe set of BSs 102 a, 102 b, 110 a and 110 b, and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, for example, directly or indirectly via a wireless orwireline backhaul.

In some aspects, a cell may not be stationary, rather, the geographicarea of the cell may move in accordance with the location of a mobileBS. In some aspects, the BSs may be interconnected to one another or toone or more other BSs or network nodes (not shown) in the wirelessnetwork through various types of backhaul interfaces such as a directphysical connection, a virtual network, or the like, or combinationsthereof using any suitable transport network.

The wireless network may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (for example, a BS or a UE) and send a transmission of the datato a downstream station (for example, a UE or a BS). A relay station mayalso be a UE that can relay transmissions for other UEs. In the exampleshown in FIG. 1, a relay station 110 d may communicate with macro BS 110a and a UE 120 d in order to facilitate communication between BS 110 aand UE 120 d. A relay station may also be referred to as a relay BS, arelay base station, a relay, or the like, or combinations thereof.

UEs 120 (for example, 120 a, 120 b, 120 c) may be dispersed throughoutthe wireless network, and each UE may be stationary or mobile. A UE mayalso be referred to as an access terminal, a terminal, a mobile station,a subscriber unit, a station, or the like, or combinations thereof. A UEmay be a cellular phone (for example, a smart phone), a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, a tablet, a camera, a gaming device, a netbook, asmartbook, an ultrabook, a medical device or equipment, biometricsensors/devices, wearable devices (smart watches, smart clothing, smartglasses, smart wrist bands, smart jewelry (for example, smart ring,smart bracelet)), an entertainment device (for example, a music or videodevice, or a satellite radio), a vehicular component or sensor, smartmeters/sensors, industrial manufacturing equipment, a global positioningsystem device, or any other suitable device that is configured tocommunicate via a wireless medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, sensors, meters,monitors, location tags, or the like, or combinations thereof, that maycommunicate with a base station, another device (for example, remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (for example, a wide area network suchas Internet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices, ormay be implemented as NB-IoT (narrowband internet of things) devices.Some UEs may be considered a Customer Premises Equipment (CPE). UE 120may be included inside a housing that houses components of UE 120, suchas processor components, memory components, or the like, or combinationsthereof.

In general, any quantity of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies orfrequency channels. A frequency may also be referred to as a carrier orthe like, or combinations thereof. Each frequency may support a singleRAT in a given geographic area in order to avoid interference betweenwireless networks of different RATs. In some cases, NR or 5G RATnetworks may be deployed.

In some aspects, two or more UEs 120 (for example, shown as UE 120 a andUE 120 e) may communicate directly with one another using one or moresidelink channels (for example, without using a base station 110 as anintermediary). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (for example,which may include a vehicle-to-vehicle (V2V) protocol, avehicle-to-infrastructure (V2I) protocol, or the like, or combinationsthereof), a mesh network, or the like, or combinations thereof. In thiscase, the UE 120 may perform scheduling operations, resource selectionoperations, or other operations described elsewhere herein as beingperformed by the base station 110.

FIG. 2 is a block diagram illustrating an example base station (BS) incommunication with a user equipment (UE) in a wireless network inaccordance with various aspects of the present disclosure. Base station110 may be equipped with T antennas 234 a through 234 t, and UE 120 maybe equipped with R antennas 252 a through 252 r, where in general T≥1and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCSs) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (for example,encode) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (for example, forsemi-static resource partitioning information (SRPI) or the like, orcombinations thereof) and control information (for example, CQIrequests, grants, upper layer signaling, or the like, or combinationsthereof) and provide overhead symbols and control symbols. Transmitprocessor 220 may also generate reference symbols for reference signals(for example, the cell-specific reference signal (CRS)) andsynchronization signals (for example, the primary synchronization signal(PSS) and secondary synchronization signal (SSS)). A transmit (TX)multiple-input multiple-output (MIMO) processor 230 may perform spatialprocessing (for example, precoding) on the data symbols, the controlsymbols, the overhead symbols, or the reference symbols, if applicable,and may provide T output symbol streams to T modulators (MODs) 232 athrough 232 t. Each MOD 232 may process a respective output symbolstream (for example, for OFDM or the like, or combinations thereof) toobtain an output sample stream. Each MOD 232 may further process (forexample, convert to analog, amplify, filter, and upconvert) the outputsample stream to obtain a downlink signal. T downlink signals from MODs232 a through 232 t may be transmitted via T antennas 234 a through 234t, respectively. In accordance with various aspects described in moredetail below, the synchronization signals can be generated with locationencoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 or other base stations and may provide receivedsignals to R demodulators (DEMODs) 254 a through 254 r, respectively.Each DEMOD 254 may condition (for example, filter, amplify, downconvert,and digitize) a received signal to obtain input samples. Each DEMOD 254may further process the input samples (for example, for OFDM or thelike, or combinations thereof) to obtain received symbols. A MIMOdetector 256 may obtain received symbols from all R DEMODs 254 a through254 r, perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 258 may process (forexample, decode) the detected symbols, provide decoded data for UE 120to a data sink 260, and provide decoded control information and systeminformation to a controller/processor 280. A channel processor maydetermine a reference signal received power (RSRP), a received signalstrength indicator (RSSI), a reference signal received quality (RSRQ), achannel quality indicator (CQI), or the like, or combinations thereof.In some aspects, one or more components of UE 120 may be included in ahousing.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 as well as control information (forexample, for reports including RSRP, RSSI, RSRQ, CQI, or the like, orcombinations thereof) from controller/processor 280. Transmit processor264 may also generate reference symbols for one or more referencesignals. The symbols from transmit processor 264 may be precoded by a TXMIMO processor 266 if applicable, further processed by MODs 254 athrough 254 r (for example, for discrete Fourier transform spreadorthogonal frequency division multiplexing (DFT-s-OFDM), orthogonalfrequency division multiplexing (OFDM) with a cyclic prefix (CP)(CP-OFDM), or the like, or combinations thereof), and transmitted tobase station 110. At base station 110, the uplink signals from UE 120and other UEs may be received by antennas 234, processed by DEMODs 232,detected by a MIMO detector 236 if applicable, and further processed bya receive processor 238 to obtain decoded data and control informationsent by UE 120. Receive processor 238 may provide the decoded data to adata sink 239 and the decoded control information tocontroller/processor 240. Base station 110 may include communicationunit 244 and communicate to network controller 130 via communicationunit 244. Network controller 130 may include communication unit 294,controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280of UE 120, or any other component(s) of FIG. 2 may perform one or moretechniques associated with scheduling broadcast or multicastcommunications, as described in more detail elsewhere herein. Forexample, controller/processor 240 of base station 110,controller/processor 280 of UE 120, or any other component(s) of FIG. 2may perform or direct operations of, for example, the process of FIG. 4,the process of FIG. 5, or other processes as described herein. Memories242 and 282 may store data and program codes for base station 110 and UE120, respectively. A scheduler 246 may schedule UEs for datatransmission on the downlink or uplink.

In some aspects, UE 120 may include means for receiving abroadcast/multicast scheduling configuration for a physical downlinkcontrol channel (PDCCH), the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or morebandwidth parts (BWPs), means for receiving a broadcast/multicastcommunication associated with a broadcast/multicast control channel(MCCH) or a broadcast/multicast traffic channel (MTCH) via a physicaldownlink shared channel (PDSCH) in accordance with thebroadcast/multicast scheduling configuration for the PDCCH, or the like,or combinations thereof. In some aspects, such means may include one ormore components of UE 120 described in connection with FIG. 2.

In some aspects, base station 110 may include means for transmitting, toa plurality of UEs, a broadcast/multicast scheduling configuration for aPDCCH, the broadcast/multicast scheduling configuration identifying, forreceiving broadcast/multicast communications, at least one of: aplurality of RNTIs that are respectively associated with a plurality ofbeams, or one or more BWPs, means for transmitting, to the plurality ofUEs, a broadcast/multicast communication associated with an MCCH or anMTCH via a PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH, or the like, or combinations thereof. Insome aspects, such means may include one or more components of basestation 110 described in connection with FIG. 2.

Some wireless networks may support broadcast/multicast communications,which may be useful for broad dissemination of information, such asemergency alerts, audio content, or video content. However, there maynot be mechanisms for scheduling broadcast/multicast communications frommultiple cells or using multiple beams. Moreover, there may not bemechanisms for retransmission of broadcast/multicast communications to aparticular UE when broadcast/multicast traffic is multiplexed withunicast traffic.

Some techniques and apparatuses described herein facilitate schedulingbroadcast/multicast communications. For example, a schedulingconfiguration for broadcast/multicast communications may define aplurality of RNTIs for a broadcast/multicast service, each of which aremapped to a particular beam, to enable a UE to receivebroadcast/multicast communications using multiple beams. As anotherexample, the scheduling configuration may define a mapping of unicastHARQ process identifiers to multicast HARQ process identifiers to enableretransmission of a broadcast/multicast communication to a particularUE. In addition, some techniques and apparatuses described hereinfacilitate scheduling broadcast/multicast communications from multiplecells. In this way, performance, reliability, and efficiency ofbroadcast/multicast communications may be improved.

FIG. 3 is a diagram illustrating an example of schedulingbroadcast/multicast communications in accordance with various aspects ofthe present disclosure. As shown in FIG. 3, a base station 110 mayschedule and transmit a broadcast/multicast communication to a UE 120.In some aspects, the UE 120 may be one of a plurality of UEs associatedwith a cell or a multicast group, and the base station 110 may scheduleand transmit a broadcast/multicast communication to the plurality ofUEs.

In some aspects, the base station 110 may transmit a broadcast/multicastcontrol communication that provides control information associated witha broadcast/multicast data communication. The broadcast/multicastcontrol communication may be carried in a logical channel associatedwith broadcast/multicast control communications. For example, thelogical channel may be an MCCH that is carried in a PDSCH. Thebroadcast/multicast data communication may be carried in a logicalchannel associated with broadcast/multicast data communications. Forexample, the logical channel may be an MTCH that is carried in thePDSCH.

The broadcast/multicast control communication of the MCCH and thebroadcast/multicast data communication of the MTCH each may be scheduledby downlink control information (DCI) carried in a PDCCH. A cyclicredundancy check (CRC) of the DCI scheduling the broadcast/multicastcontrol communication of the MCCH may be scrambled by a multicast RNTI(M-RNTI). A CRC of the DCI scheduling the broadcast/multicast datacommunication of the MTCH may be scrambled by a group RNTI (G-RNTI).

As shown in FIG. 3, in a first operation 310, the base station 110 maytransmit, and the UE 120 may receive, a broadcast/multicast schedulingconfiguration. For example, the base station 110 may transmit thebroadcast/multicast scheduling configuration in response to abroadcast/multicast interest indication message received from the UE120. The broadcast/multicast interest indication message may include atemporary mobile group identifier (TMGI) or a quality of service (QoS)identifier that identifies a broadcast/multicast service to which the UE120 is to be subscribed. As another example, the base station 110 maybroadcast the broadcast/multicast scheduling configuration to all UEs ina cell served by the base station 110.

The base station 110 may transmit the broadcast/multicast schedulingconfiguration via a system information block (SIB) or radio resourcecontrol (RRC) signaling carried in the PDSCH. The broadcast/multicastscheduling configuration may include scheduling information forobtaining DCI carried on the PDCCH. In addition, the broadcast/multicastscheduling configuration may define one or more broadcast/multicastparameters for the UE 120. The one or more broadcast/multicastparameters may be associated with obtaining the broadcast/multicastcontrol communication on the MCCH or obtaining the broadcast/multicastdata communication on the MTCH.

In some aspects, the broadcast/multicast scheduling configuration mayidentify a plurality of RNTIs associated with a broadcast/multicastservice (for example, a broadcast/multicast service identified by a TMGIor a QoS identifier). The plurality of RNTIs may include a first set ofRNTIs that are associated with the MCCH (for example, M-RNTIs) or asecond set of RNTIs that are associated with the MTCH (for example,G-RNTIs). Moreover, each RNTI of the plurality of RNTIs may identify arespective beam of a plurality of beams (for example, a plurality oftransmission configuration indicator (TCI) states corresponding to theplurality of beams). In this way, the base station 110 may transmit acommunication for a broadcast/multicast service using multiple beams,thereby improving reliability and network capacity forbroadcast/multicast communications.

In some aspects, the broadcast/multicast scheduling configuration mayidentify time-domain scheduling information (for example, one or moreconfigurations for a time-domain resource allocation). For example, thebroadcast/multicast scheduling configuration may identify a periodicityor a window duration associated with the DCI carried on the PDCCH. Asanother example, the broadcast/multicast scheduling configuration mayprovide information to enable the UE 120 to identify repetitions of abroadcast/multicast communication. In some aspects, thebroadcast/multicast scheduling configuration may configure particularquantities of repetitions for particular beams (for example, particularTCI states). For example, the broadcast/multicast schedulingconfiguration may configure a greater quantity of repetitions for awider beam (for example, a wider beam used to transmit thebroadcast/multicast control communication of the MCCH) and a lesserquantity of repetitions for a narrower beam (for example, a narrowerbeam used to transmit the broadcast/multicast data communication of theMTCH). Moreover, the broadcast/multicast scheduling configuration mayidentify a plurality of time offsets associated with a plurality ofbeams (for example, the plurality of beams associated with the pluralityof RNTIs). For example, a time offset may identify a slot or a symbol inwhich a particular beam is to transmit a broadcast/multicastcommunication. The plurality of time offsets may include a first set oftime offsets that are associated with the MCCH or a second set of timeoffsets that are associated with the MTCH.

In some aspects, the broadcast/multicast scheduling configuration mayidentify frequency-domain scheduling information (for example, one ormore configurations for a frequency-domain resource allocation). Forexample, the broadcast/multicast scheduling configuration may identifyone or more BWPs in which the UE 120 is to receive a broadcast/multicastcommunication. The one or more BWPs may include a first set of BWPs thatare associated with the MCCH or a second set of BWPs that are associatedwith the MTCH. In some aspects, the first set of BWPs and the second setof BWPs may be the same or different (for example, the first set and thesecond set may differ by at least one BWP). In addition, thebroadcast/multicast scheduling configuration may identify afrequency-hopping pattern. For example, the frequency-hopping patternmay identify a pattern of frequencies within a BWP, or across multipleBWPs, on which the UE 120 is to receive a broadcast/multicastcommunication, thereby improving transmission diversity for thebroadcast/multicast communication.

In some aspects, the broadcast/multicast scheduling configuration mayidentify a plurality of control resource set (CORESET) configurationsand search space configurations for a BWP. A CORESET configuration mayinclude a beam configuration (for example, a TCI state of a beam). Theplurality of CORESET configurations and search space configurations mayinclude a first set of CORESET configurations and search spaceconfigurations that are associated with the MCCH and a second set ofCORESET configurations and search space configurations associated withthe MTCH.

In some aspects, the broadcast/multicast scheduling configuration mayidentify (for example, for a UE in a connected mode (RRC_CONNECTED)) amapping of unicast HARQ process identifiers to broadcast/multicast HARQprocess identifiers (for example, virtual broadcast/multicast HARQprocess identifiers). For example, the mapping may identify arelationship between a particular HARQ process identifier associatedwith a cell RNTI (C-RNTI) for unicast transmissions and a particularHARQ process identifier associated with a G-RNTI or an M-RNTI forbroadcast/multicast transmissions. In this way, the mapping enables theUE 120 to receive unicast retransmissions of a broadcast/multicastcommunication.

In some aspects, the broadcast/multicast scheduling configuration mayidentify a demodulation reference signal (DMRS) scrambling identifier,which may be used as an identifier of a single cell or an identifier ofmultiple cells of an SFN. A default value of the DMRS scramblingidentifier may be a physical cell identifier of a serving cell. In someaspects, the broadcast/multicast scheduling configuration may identify atimeline configuration relating to a timeline for processing of thePDCCH, receiving a broadcast/multicast communication, and transmittingacknowledgment (ACK) or negative ACK (NACK) feedback to thebroadcast/multicast communication. In such cases, the timeline may beconfigured to have a different duration than a corresponding unicasttimeline. For example, the timeline may have a greater duration than acorresponding unicast timeline, thereby providing additional time(relative to unicast) for the base station 110 to determine whether abroadcast/multicast communication is to be retransmitted bybroadcast/multicast or unicast. In some aspects, a duration of thetimeline may be greater than a slowest processing time among UEsreceiving a broadcast/multicast communication (for example, based atleast in part on reported UE capabilities).

In a second operation 320, the base station 110 may transmit, and the UE120 may receive, DCI associated with the MCCH. For example, the UE 120may monitor the PDCCH in accordance with the broadcast/multicastscheduling configuration in order to obtain the DCI. The DCI may includea downlink grant for accessing a broadcast/multicast controlcommunication of the MCCH on the PDSCH.

The DCI may identify (for example, according to a selection made by thebase station 110) a particular broadcast/multicast parameter that the UE120 is to use to obtain the broadcast/multicast control communication onthe MCCH. In some aspects, the DCI may identify a particular RNTI (forexample, an M-RNTI) of the plurality of RNTIs configured in thescheduling configuration. For example, the DCI may be scrambled by theidentified RNTI. As described above, the identified RNTI may correspondto a particular beam (for example, a particular TCI state).Additionally, the DCI may identify a particular time offset of theplurality of time offsets configured in the scheduling configuration.The identified time offset may identify a slot or a symbol in which theparticular beam is to transmit the broadcast/multicast controlcommunication. In this way, the DCI may indicate a particular beam ortime offset that the UE 120 is to use to obtain the broadcast/multicastcontrol communication, which may be useful when the UE 120 is inoverlapping beam coverage.

In some aspects, the DCI may identify a particular BWP of the pluralityof BWPs configured in the scheduling configuration. The identified BWP,for example, may be associated with a particular broadcast/multicastservice, a particular QoS, or a particular PDSCH configuration. In someaspects, the DCI may identify a particular CORESET configuration andsearch space configuration of the plurality of CORESET configurationsand search space configurations configured in the schedulingconfiguration. The identified CORESET configuration and search spaceconfiguration may be associated with the particular BWP. In addition,the DCI may identify a particular resource block (RB) allocation in theidentified BWP.

In some aspects, the DCI may identify a particular MCS that the UE 102is to use to decode the broadcast/multicast control communication.Moreover, the DCI may identify a HARQ process identifier that the UE 102is to use for the broadcast/multicast control communication. Theidentified HARQ process identifier for the broadcast/multicast controlcommunication may be mapped to a particular unicast HARQ processidentifier in the broadcast/multicast scheduling configuration, asdescribed above.

In some aspects, the DCI may be in DCI format 1_0 or 1_1. In someaspects, the DCI, in format 1_0, may be in a compact format that isscrambled by a particular M-RNTI (for example, a multicast new RNTI(M-N-RNTI)) defined for indicating a change to a broadcast/multicastcontrol communication. In such a compact format, the DCI may allocate 8bits to indicate a change to a broadcast/multicast control communicationand may allocate 2 bits to indicate an update of system information.

In a third operation 330, the base station 110 may transmit, and the UE120 may receive, the broadcast/multicast control communication. Forexample, the UE 120 may monitor the PDSCH in accordance with the DCI inorder to obtain the broadcast/multicast control communication on theMCCH. The broadcast/multicast control communication may identify a TMGIfor the broadcast/multicast service, a broadcast/multicast sessionidentifier, a G-RNTI used to scramble DCI associated with the MTCH, anda broadcast/multicast scheduling configuration. The broadcast/multicastscheduling configuration may include scheduling information for the DCIassociated with the MTCH, and in some cases may define, or redefine, oneor more of the broadcast/multicast parameters for the UE 120, asdescribed above.

In some aspects, the UE 120 may receive the broadcast/multicast controlcommunication from a single cell (for example, the base station 110 maybe included in the single cell) of a wireless network. In such a case,the UE 120 may receive the broadcast/multicast control communicationbased at least in part on whether the wireless network supports theMCCH.

In a scenario in which the wireless network does not support the MCCH,the UE 120 may receive the broadcast/multicast control communication viaa SIB or RRC signaling from the single cell. For example, if the UE 120is in a connected mode, the UE 120 may receive (for example, in responseto a request made by the UE 120 for a broadcast/multicast service) thebroadcast/multicast control communication via RRC signaling (forexample, unicast RRC signaling). In such a case, scheduling in the PDCCHfor the broadcast/multicast control communication may be provided by DCIscrambled by a C-RNTI. As another example, if the UE 120 is in aninactive mode or an idle mode, the UE 120 may receive thebroadcast/multicast control communication via a SIB. In such a case,scheduling in the PDCCH for the broadcast/multicast controlcommunication may be provided by DCI scrambled by a system informationRNTI (SI-RNTI). In some aspects, the SIB may use a particular SI-RNTIdefined for broadcast/multicast.

In a case in which the wireless network supports the MCCH, thebroadcast/multicast control communication may be carried in the MCCH andscheduled in the PDCCH by DCI scrambled by an M-RNTI (for example, anM-RNTI corresponding to a particular beam selected by the base station110), as described above. Furthermore, in such a case, the UE 120 maymonitor the PDCCH for the DCI using a CORESET configuration and searchspace configuration associated with the single cell.

In some aspects, the UE 120 may receive the broadcast/multicast controlcommunication from multiple cells (for example, multiple cells of anSFN). In such a case, the DCI carried in the PDCCH may be provided by aserving cell (for example, the base station 110 may be included in theserving cell) of the multiple cells, or by the multiple cells. In ascenario in which the DCI is provided by the serving cell, the UE 120may monitor the PDCCH for the DCI using a CORESET configuration andsearch space configuration indicated in a broadcast/multicast schedulingconfiguration transmitted by the serving cell. In a scenario in whichDCIs are provided by the multiple cells, the UE 120 may monitor thePDCCH for the DCIs using CORESET configurations and search spaceconfigurations indicated in broadcast/multicast schedulingconfigurations transmitted from the multiple cells. In some aspects, afirst set of multiple cells may transmit the DCIs and a second set ofmultiple cells may transmit the broadcast/multicast controlcommunication. The first set of multiple cells and the second set ofmultiple cells may be the same or different (for example, the first setand the second set may differ by at least one cell).

In some aspects, the UE 120 may transmit ACK or NACK feedback for thebroadcast/multicast control communication to the base station 110. Forexample, the UE 120 may transmit NACK feedback to thebroadcast/multicast control communication using a broadcast/multicastHARQ process identifier associated with the broadcast/multicast controlcommunication. In some aspects, the base station 110 may determine toretransmit the broadcast/multicast control communication as one or moreunicast retransmissions or as a broadcast/multicast retransmission basedat least in part on a quantity of NACK feedback messages received fromUEs.

For example, the base station 110 may determine that the quantity ofNACK feedback messages to the broadcast/multicast control communicationsatisfies a threshold value, and may retransmit the broadcast/multicastcontrol communication as a broadcast/multicast retransmission using thebroadcast/multicast HARQ process identifier. Alternatively, the basestation 110 may determine that the quantity of NACK feedback messages tothe broadcast/multicast control communication does not satisfy athreshold value (for example, if the UE 120 was the only UE reportingNACK feedback), and may retransmit the broadcast/multicast controlcommunication as a unicast retransmission, using a unicast HARQ processidentifier, to the UE 120. In such a case, the base station 110 may usethe mapping of unicast HARQ process identifiers and broadcast/multicastHARQ process identifiers indicated in the broadcast/multicast schedulingconfiguration to select the unicast HARQ process identifier associatedwith the broadcast/multicast control communication. Moreover, the UE 120may receive the unicast retransmission and identify the unicastretransmission as a retransmission of the broadcast/multicast controlcommunication based at least in part on the mapping of unicast HARQprocess identifiers and broadcast/multicast HARQ process identifiersindicated in the broadcast/multicast scheduling configuration.

In a fourth operation 340, the base station 110 may transmit, and the UE120 may receive, DCI associated with the MTCH. For example, the UE 120may monitor the PDCCH in accordance with the broadcast/multicast controlcommunication in order to obtain the DCI. The DCI may include a downlinkgrant for accessing a broadcast/multicast data communication on thePDSCH.

The DCI may identify (for example, according to a selection made by thebase station 110) a particular broadcast/multicast parameter that the UE120 is to use to obtain the broadcast/multicast data communication, in amanner similar to that described above in connection with the DCI forthe MCCH. For example, the DCI may identify an RNTI (for example, aG-RNTI) from a plurality of RNTIs indicated in the broadcast/multicastscheduling configuration. As another example, the DCI may identify atime offset from a plurality of time offsets indicated in thebroadcast/multicast scheduling configuration. As a further example, theDCI may identify a BWP from a plurality of BWPs indicated in thebroadcast/multicast scheduling configuration. As an additional example,the DCI may identify a CORESET configuration and search spaceconfiguration from a plurality of CORESET configurations and searchspace configurations indicated in the broadcast/multicast schedulingconfiguration.

In addition, the DCI may identify a particular MCS that the UE 102 is touse to decode the broadcast/multicast data communication. Moreover, theDCI may identify a HARQ process identifier that the UE 102 is to use forthe broadcast/multicast data communication. The identified HARQ processidentifier for the broadcast/multicast data communication may be mappedto a particular unicast HARQ process identifier in thebroadcast/multicast scheduling configuration, as described above.

In this way, the broadcast/multicast scheduling configuration enablesthe base station 110 to select different broadcast/multicast parametersfor the broadcast/multicast control communication on the MCCH and thebroadcast/multicast data communication on the MTCH. For example, thebase station 110 may select one or more wider beams for transmission ofthe broadcast/multicast control communication and may select one or morenarrower beams for transmission of the broadcast/multicast datacommunication. As another example, the base station 110 may select anMCS with a lower data rate for transmission of the broadcast/multicastcontrol communication and may select an MCS with a higher data rate fortransmission of the broadcast/multicast data communication.

In a fifth operation 350, the base station 110 may transmit, and the UE120 may receive, the broadcast/multicast data communication. Forexample, the UE 120 may monitor the PDSCH in accordance with the DCI inorder to obtain the broadcast/multicast data communication on the MTCH.The broadcast/multicast data communication may provide an emergencyalert, audio content, video content, or the like to the UE 120.

In some aspects, the UE 120 may receive the broadcast/multicast datacommunication from a single cell (for example, the base station 110 maybe included in the single cell) of a wireless network. For example, thebroadcast/multicast data communication may be carried in the MTCH andscheduled in the PDCCH by DCI scrambled by a G-RNTI (for example, aG-RNTI corresponding to a particular beam selected by the base station110), as described above.

In some aspects, the UE 120 may receive the broadcast/multicast datacommunication from multiple cells (for example, multiple cells of anSFN). In such a case, the DCI carried in the PDCCH may be provided by aserving cell (for example, the base station 110 may be included in theserving cell) of the multiple cells or by the multiple cells. In ascenario in which the DCI is provided by the serving cell, the UE 120may monitor the PDCCH for the DCI using a CORESET configuration andsearch space configuration indicated in a broadcast/multicast schedulingconfiguration transmitted by the serving cell, and the UE 120 maymonitor the PDSCH for the broadcast/multicast data communication using aCORESET configuration and search space configuration indicated in abroadcast/multicast control communication transmitted by the servingcell. In a scenario in which DCIs are provided by the multiple cells,the UE 120 may monitor the PDCCH for the DCIs using CORESETconfigurations and search space configurations indicated inbroadcast/multicast control communications transmitted by the multiplecells. In some aspects, a first set of multiple cells may transmit theDCIs and a second set of multiple cells may transmit thebroadcast/multicast data communication. The first set of multiple cellsand the second set of multiple cells may be the same or different (forexample, the first set and the second set may differ by at least onecell).

In some aspects, the UE 120 may transmit ACK or NACK feedback for thebroadcast/multicast data communication to the base station 110. Forexample, the UE 120 may transmit NACK feedback to thebroadcast/multicast data communication using a broadcast/multicast HARQprocess identifier associated with the broadcast/multicast datacommunication. In some aspects, the base station 110 may determine toretransmit the broadcast/multicast data communication as one or moreunicast retransmissions or as a broadcast/multicast retransmission basedat least in part on a quantity of NACK feedback messages received fromUEs, in a manner similar to that described above for retransmission ofthe broadcast/multicast control communication.

FIG. 4 is a diagram illustrating an example process 400 performed, forexample, by a UE, in accordance with various aspects of the presentdisclosure. The example process 400 is an example where a UE, such as UE120, performs operations associated with scheduling broadcast/multicastcommunications.

As shown in FIG. 4, in some aspects, the process 400 may includereceiving a broadcast/multicast scheduling configuration for a PDCCH,the broadcast/multicast scheduling configuration identifying, forreceiving broadcast/multicast communications, at least one of: aplurality of RNTIs that are respectively associated with a plurality ofbeams, or one or more BWPs (block 410). For example, the UE (usingreceive processor 258, controller/processor 280, or memory 282, amongother possibilities/examples) may receive a broadcast/multicastscheduling configuration for a PDCCH, the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or more BWPs,as described above.

As further shown in FIG. 4, in some aspects, the process 400 may includereceiving a broadcast/multicast communication associated with an MCCH oran MTCH via a PDSCH in accordance with the broadcast/multicastscheduling configuration for the PDCCH (block 420). For example, the UE(using receive processor 258, controller/processor 280, or memory 282,among other possibilities/examples) may receive a broadcast/multicastcommunication associated with an MCCH or an MTCH via a PDSCH inaccordance with the broadcast/multicast scheduling configuration for thePDCCH, as described above.

The process 400 of FIG. 4 may include additional aspects, such as anysingle aspect or any combination of aspects described below or inconnection with one or more other processes described elsewhere herein.

In a first aspect, the broadcast/multicast communication is associatedwith an MCCH or an MTCH. In a second additional aspect, alone or incombination with the first aspect, the control channel is a PDCCH andthe shared channel is a PDSCH, and the PDCCH provides scheduling for thebroadcast/multicast communication associated with the MCCH or the MTCHon the PDSCH.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of RNTIs associated withbroadcast/multicast communication. In a fourth additional aspect, aloneor in combination with one or more of the first through third aspects,the plurality of RNTIs are multicast RNTIs relating to abroadcast/multicast control channel. In a fifth additional aspect, aloneor in combination with one or more of the first through fourth aspects,the plurality of RNTIs are group RNTIs relating to a broadcast/multicasttraffic channel.

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, each RNTI of the plurality of RNTIsidentifies a respective beam of a plurality of beams for receiving thebroadcast/multicast communication. In a seventh additional aspect, aloneor in combination with one or more of the first through sixth aspects,the process 400 further includes receiving control information thatidentifies a particular RNTI of the plurality of RNTIs, and thebroadcast/multicast communication is received in accordance with theparticular RNTI.

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of time offsets associated with theplurality of beams. In a ninth additional aspect, alone or incombination with one or more of the first through eighth aspects, theprocess 400 further includes receiving control information thatidentifies a particular time offset of the plurality of time offsets,and the broadcast/multicast communication is received in accordance withthe particular time offset.

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, the broadcast/multicast schedulingconfiguration provides information relating to identification ofrepetitions of the broadcast/multicast communication. For example, thebroadcast/multicast scheduling configuration may configure particularquantities of repetitions for particular beams.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, the broadcast/multicastscheduling configuration identifies one or more BWPs for receiving thebroadcast/multicast communication. In a twelfth additional aspect, aloneor in combination with one or more of the first through eleventhaspects, the process 400 further includes receiving control informationthat identifies a particular BWP of the one or more BWPs, and thebroadcast/multicast communication is received in accordance with theparticular BWP.

In a thirteenth additional aspect, alone or in combination with one ormore of the first through twelfth aspects, the broadcast/multicastscheduling configuration identifies a frequency-hopping pattern within aBWP or a frequency-hopping pattern across multiple BWPs. In a fourteenthadditional aspect, alone or in combination with one or more of the firstthrough thirteenth aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of CORESET configurations andsearch space configurations for a bandwidth part, and a CORESETconfiguration of the plurality of CORESET configurations identifies abeam configuration. In a fifteenth additional aspect, alone or incombination with one or more of the first through fourteenth aspects,the process 400 further includes receiving control information thatidentifies a particular CORESET configuration and search spaceconfiguration of the plurality of CORESET configurations and searchspace configurations, and the broadcast/multicast communication isreceived in accordance with the particular CORESET configuration andsearch space configuration.

In a sixteenth additional aspect, alone or in combination with one ormore of the first through fifteenth aspects, the broadcast/multicastscheduling configuration identifies a mapping of unicast HARQ processidentifiers to broadcast/multicast HARQ process identifiers.Accordingly, the process 400 may further include transmitting HARQfeedback for the broadcast/multicast communication. Here, the UE mayreceive a unicast retransmission of the broadcast/multicastcommunication that identifies a unicast HARQ process identifier, whichis mapped to a broadcast/multicast HARQ process identifier associatedwith the broadcast/multicast communication.

In a seventeenth additional aspect, alone or in combination with one ormore of the first through sixteenth aspects, the broadcast/multicastscheduling configuration identifies a DMRS scrambling identifier.

In an eighteenth additional aspect, alone or in combination with one ormore of the first through seventeenth aspects, the broadcast/multicastscheduling configuration identifies a timeline configuration thatindicates a first time duration between processing of the PDCCH andreceiving the broadcast/multicast communication, and a second timeduration between receiving the broadcast/multicast communication andtransmitting acknowledgment or negative-acknowledgment feedback, andeach of the first time duration and the second time duration isdifferent than a corresponding time duration for a unicast transmission.

In a nineteenth additional aspect, alone or in combination with one ormore of the first through eighteenth aspects, the process 400 furtherincludes receiving, from a single cell, control information thatschedules the broadcast/multicast communication in the shared channel,and the broadcast/multicast communication is received from multiplecells of a single frequency network. In a twentieth additional aspect,alone or in combination with one or more of the first through nineteenthaspects, the control information is received via unicast signaling. In atwenty-first additional aspect, alone or in combination with one or moreof the first through twentieth aspects, the process 400 further includesreceiving, from a first group of one or more cells with an SFN, controlinformation that schedules the broadcast/multicast communication in thePDSCH, and the broadcast/multicast communication is received from asecond group of one or more cells with an SFN.

In a twenty-second additional aspect, alone or in combination with oneor more of the first through twenty-first aspects, the process 400further includes receiving control information scrambled by a particularRNTI, and the particular RNTI indicates a change to thebroadcast/multicast communication.

FIG. 5 is a diagram illustrating an example process 500 performed, forexample, by a base station, in accordance with various aspects of thepresent disclosure. The example process 500 is an example where a basestation, such as base station 110, performs operations associated withscheduling broadcast/multicast communications.

As shown in FIG. 5, in some aspects, the process 500 may includetransmitting, to a plurality of UEs, a broadcast/multicast schedulingconfiguration for a PDCCH, the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or more BWPs(block 510). For example, the base station (using transmit processor220, controller/processor 240, memory 242, among otherpossibilities/examples) may transmit, to a plurality of UEs, abroadcast/multicast scheduling configuration for a PDCCH, thebroadcast/multicast scheduling configuration identifying, for receivingbroadcast/multicast communications, at least one of a plurality of RNTIsthat are respectively associated with a plurality of beams, or one ormore BWPs, as described above.

As further shown in FIG. 5, in some aspects, the process 500 may includetransmitting, to the plurality of UEs, a broadcast/multicastcommunication associated with an MCCH or an MTCH via a PDSCH inaccordance with the broadcast/multicast scheduling configuration for thePDCCH (block 520). For example, the base station (using transmitprocessor 220, controller/processor 240, memory 242, among otherpossibilities/examples) may transmit, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH, as described above.

The process 500 of FIG. 5 may include additional aspects, such as anysingle aspect or any combination of aspects described below or inconnection with one or more other processes described elsewhere herein.

In a first aspect, the broadcast/multicast communication is associatedwith an MCCH or an MTCH. In a second additional aspect, alone or incombination with the first aspect, the control channel is a PDCCH andthe shared channel is a PDSCH, and the PDCCH schedules thebroadcast/multicast communication associated with the MCCH or the MTCHon the PDSCH.

In a third additional aspect, alone or in combination with one or moreof the first and second aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of RNTIs associated withbroadcast/multicast communication. In a fourth additional aspect, aloneor in combination with one or more of the first through third aspects,the plurality of RNTIs are multicast RNTIs relating to abroadcast/multicast control channel. In a fifth additional aspect, aloneor in combination with one or more of the first through fourth aspects,the plurality of RNTIs are group RNTIs relating to a broadcast/multicasttraffic channel.

In a sixth additional aspect, alone or in combination with one or moreof the first through fifth aspects, each RNTI of the plurality of RNTIsidentifies a respective beam of a plurality of beams in which theplurality of UEs are to receive the broadcast/multicast communication.In a seventh additional aspect, alone or in combination with one or moreof the first through sixth aspects, the process 500 further includestransmitting control information that identifies a particular RNTI ofthe plurality of RNTIs, and the broadcast/multicast communication istransmitted in accordance with the particular RNTI.

In an eighth additional aspect, alone or in combination with one or moreof the first through seventh aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of time offsets associated with theplurality of beams. In a ninth additional aspect, alone or incombination with one or more of the first through eighth aspects, theprocess 500 further includes transmitting control information thatidentifies a particular time offset of the plurality of time offsets,and the broadcast/multicast communication is transmitted in accordancewith the particular time offset.

In a tenth additional aspect, alone or in combination with one or moreof the first through ninth aspects, the broadcast/multicast schedulingconfiguration provides information relating to identification ofrepetitions of the broadcast/multicast communication. For example, thebroadcast/multicast scheduling configuration may configure particularquantities of repetitions for particular beams.

In an eleventh additional aspect, alone or in combination with one ormore of the first through tenth aspects, the broadcast/multicastscheduling configuration identifies one or more BWPs in which theplurality of UEs are to receive the broadcast/multicast communication.In a twelfth additional aspect, alone or in combination with one or moreof the first through eleventh aspects, the process 500 further includestransmitting control information that identifies a particular BWP of theone or more BWPs, and the broadcast/multicast communication istransmitted in accordance with the particular BWP.

In a thirteenth additional aspect, alone or in combination with one ormore of the first through twelfth aspects, the broadcast/multicastscheduling configuration identifies a frequency-hopping pattern within aBWP or a frequency-hopping pattern across multiple BWPs. In a fourteenthadditional aspect, alone or in combination with one or more of the firstthrough thirteenth aspects, the broadcast/multicast schedulingconfiguration identifies a plurality of CORESET configurations andsearch space configurations for a bandwidth part, and a CORESETconfiguration of the plurality of CORESET configurations identifies abeam configuration. In a fifteenth additional aspect, alone or incombination with one or more of the first through fourteenth aspects,the process 500 further includes transmitting control information thatidentifies a particular CORESET configuration and search spaceconfiguration of the plurality of CORESET configurations and searchspace configurations, and the broadcast/multicast communication istransmitted in accordance with the particular CORESET configuration andsearch space configuration.

In a sixteenth additional aspect, alone or in combination with one ormore of the first through fifteenth aspects, the broadcast/multicastscheduling configuration identifies a mapping of unicast HARQ processidentifiers to broadcast/multicast HARQ process identifiers associatedwith the broadcast/multicast communication. Accordingly, the process 500may further include receiving HARQ feedback for the broadcast/multicastcommunication. Here, the base station may transmit a unicastretransmission of the broadcast/multicast communication that identifiesa unicast HARQ process identifier, which is mapped to abroadcast/multicast HARQ process identifier associated with thebroadcast/multicast communication.

In a seventeenth additional aspect, alone or in combination with one ormore of the first through sixteenth aspects, the broadcast/multicastscheduling configuration identifies a DMRS scrambling identifier.

In an eighteenth additional aspect, alone or in combination with one ormore of the first through seventeenth aspects, the broadcast/multicastscheduling configuration identifies a timeline configuration thatindicates a first time duration between processing of the PDCCH andreceiving the broadcast/multicast communication by a UE, and a secondtime duration between receiving the broadcast/multicast communicationand transmitting acknowledgment or negative-acknowledgment feedback by aUE, and each of the first time duration and the second time duration isdifferent than a corresponding time duration for unicast transmissions.

In a nineteenth additional aspect, alone or in combination with one ormore of the first through eighteenth aspects, the process 500 furtherincludes transmitting control information scrambled by a particularRNTI, and the particular RNTI indicates a change to thebroadcast/multicast communication.

FIG. 6 is a block diagram of an example apparatus 600 for wirelesscommunication in accordance with various aspects of the presentdisclosure. The apparatus 600 may be a UE, or a UE may include theapparatus 600. In some aspects, the apparatus 600 includes a receptioncomponent 602, a communication manager 604, and a transmission component606, which may be in communication with one another (for example, viaone or more buses). As shown, the apparatus 600 may communicate withanother apparatus 608 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 602 and thetransmission component 606.

In some aspects, the apparatus 600 may be configured to perform one ormore operations described herein in connection with FIG. 3. Additionallyor alternatively, the apparatus 600 may be configured to perform one ormore processes described herein, such as process 400 of FIG. 4. In someaspects, the apparatus 600 may include one or more components of the UEdescribed above in connection with FIG. 2.

The reception component 602 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 608. The reception component 602may provide received communications to one or more other components ofthe apparatus 600, such as the communication manager 604. In someaspects, the reception component 602 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 602 may include one or more antennas, a demodulator, a MIMOdetector, a receive processor, a controller/processor, a memory, or acombination thereof, of the UE described above in connection with FIG.2.

The transmission component 606 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 608. In some aspects, thecommunication manager 604 may generate communications and may transmitthe generated communications to the transmission component 606 fortransmission to the apparatus 608. In some aspects, the transmissioncomponent 606 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 608. In some aspects, the transmission component 606may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described above in connection with FIG.2. In some aspects, the transmission component 606 may be collocatedwith the reception component 602 in a transceiver.

The communication manager 604 may receive or may cause the receptioncomponent 602 to receive a broadcast/multicast scheduling configurationfor a PDCCH, the broadcast/multicast scheduling configurationidentifying, for receiving broadcast/multicast communications, at leastone of: a plurality of RNTIs that are respectively associated with aplurality of beams, or one or more BWPs. The communication manager 604may receive or may cause the reception component 602 to receive abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH. In some aspects, the communication manager604 may include a controller/processor, a memory, or a combinationthereof, of the UE described above in connection with FIG. 2.

In some examples, the communication manager 604 may receive or may causethe reception component 602 to receive control information thatidentifies a particular RNTI of the plurality of RNTIs, and thebroadcast/multicast communication is received in accordance with theparticular RNTI. In some aspects, the broadcast/multicast schedulingconfiguration may identify a plurality of time offsets associated withthe plurality of beams. In some examples, the communication manager 604may receive or may cause the reception component 602 to receive controlinformation that identifies a particular time offset of the plurality oftime offsets, and the broadcast/multicast communication is received inaccordance with the particular time offset. In some examples, thecommunication manager 604 may receive or may cause the receptioncomponent 602 to receive control information that identifies aparticular BWP of the one or more BWPs, and the broadcast/multicastcommunication is received in accordance with the particular BWP.

In some aspects, the broadcast/multicast scheduling configurationidentifies a plurality of CORESET configurations and search spaceconfigurations for a BWP, and a CORESET configuration of the pluralityof CORESET configurations identifies a beam configuration. In someexamples, the communication manager 604 may receive or may cause thereception component 602 to receive control information that identifies aparticular CORESET configuration and search space configuration of theplurality of CORESET configurations and search space configurations, andthe broadcast/multicast communication is received in accordance with theparticular CORESET configuration and search space configuration. In someaspects, the broadcast/multicast scheduling configuration identifies amapping of unicast HARQ process identifiers to broadcast/multicast HARQprocess identifiers associated with the broadcast/multicastcommunication.

In some examples, the communication manager 604 may transmit or maycause the transmission component 606 to transmit HARQ feedback for thebroadcast/multicast communication. In some examples, the communicationmanager 604 may receive or may cause the reception component 602 toreceive a retransmission of the broadcast/multicast communication. Insome aspects, the retransmission may be a broadcast/multicastretransmission or a unicast retransmission.

In some aspects, the communication manager 604 may include a set ofcomponents associated with performing operations described herein. Insome aspects, one or more components of the set of components mayinclude or may be implemented within a controller/processor, a memory,or a combination thereof, of the UE described above in connection withFIG. 2. Additionally or alternatively, one or more components of the setof components may be implemented at least in part as software stored ina memory. For example, a component (or a portion of a component) may beimplemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The number and arrangement of components shown in FIG. 6 are provided asan example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 6. Furthermore, two or more components shown inFIG. 6 may be implemented within a single component, or a singlecomponent shown in FIG. 6 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 6 may perform one or more functions describedas being performed by another set of components shown in FIG. 6.

FIG. 7 is a block diagram of an example apparatus 700 for wirelesscommunication in accordance with various aspects of the presentdisclosure. The apparatus 700 may be a base station, or a base stationmay include the apparatus 700. In some aspects, the apparatus 700includes a reception component 702, a communication manager 704, and atransmission component 706, which may be in communication with oneanother (for example, via one or more buses). As shown, the apparatus700 may communicate with another apparatus 708 (such as a UE, a basestation, or another wireless communication device) using the receptioncomponent 702 and the transmission component 706.

In some aspects, the apparatus 700 may be configured to perform one ormore operations described herein in connection with FIG. 3. Additionallyor alternatively, the apparatus 700 may be configured to perform one ormore processes described herein, such as process 500 of FIG. 5. In someaspects, the apparatus 700 may include one or more components of thebase station described above in connection with FIG. 2.

The reception component 702 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 708. The reception component 702may provide received communications to one or more other components ofthe apparatus 700, such as the communication manager 704. In someaspects, the reception component 702 may perform signal processing onthe received communications (such as filtering, amplification,demodulation, analog-to-digital conversion, demultiplexing,deinterleaving, de-mapping, equalization, interference cancellation, ordecoding, among other examples), and may provide the processed signalsto the one or more other components. In some aspects, the receptioncomponent 702 may include one or more antennas, a demodulator, a MIMOdetector, a receive processor, a controller/processor, a memory, or acombination thereof, of the BS described above in connection with FIG.2.

The transmission component 706 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 708. In some aspects, thecommunication manager 704 may generate communications and may transmitthe generated communications to the transmission component 706 fortransmission to the apparatus 708. In some aspects, the transmissioncomponent 706 may perform signal processing on the generatedcommunications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 708. In some aspects, the transmission component 706may include one or more antennas, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the BS described above in connection with FIG.2. In some aspects, the transmission component 706 may be collocatedwith the reception component 702 in a transceiver.

The communication manager 704 may transmit or may cause the transmissioncomponent 706 to transmit, to a plurality of UEs, a broadcast/multicastscheduling configuration for PDCCH, the broadcast/multicast schedulingconfiguration identifying, for receiving broadcast/multicastcommunications, at least one of: a plurality of RNTIs that arerespectively associated with a plurality of beams, or one or more BWPs.The communication manager 704 may transmit or may cause the transmissioncomponent 706 to transmit, to the plurality of UEs, abroadcast/multicast communication associated with an MCCH or an MTCH viaa PDSCH in accordance with the broadcast/multicast schedulingconfiguration for the PDCCH. In some aspects, the communication manager704 may include a controller/processor, a memory, a scheduler, acommunication unit, or a combination thereof, of the base stationdescribed above in connection with FIG. 2.

In some examples, the communication manager 704 may transmit or maycause the transmission component 706 to transmit control informationthat identifies a particular RNTI of the plurality of RNTIs, and thebroadcast/multicast communication is transmitted in accordance with theparticular RNTI. In some aspects, the broadcast/multicast schedulingconfiguration may identify a plurality of time offsets associated withthe plurality of beams. In some examples, the communication manager 704may transmit or may cause the transmission component 706 to transmitcontrol information that identifies a particular time offset of theplurality of time offsets, and the broadcast/multicast communication istransmitted in accordance with the particular time offset. In someexamples, the communication manager 704 may transmit or may cause thetransmission component 706 to transmit control information thatidentifies a particular BWP of the one or more BWPs, and thebroadcast/multicast communication is transmitted in accordance with theparticular BWP.

In some aspects, the broadcast/multicast scheduling configurationidentifies a plurality of CORESET configurations and search spaceconfigurations for a BWP, and a CORESET configuration of the pluralityof CORESET configurations identifies a beam configuration. In someexamples, the communication manager 704 may transmit or may cause thetransmission component 706 to transmit control information thatidentifies a particular CORESET configuration and search spaceconfiguration of the plurality of CORESET configurations and searchspace configurations, and the broadcast/multicast communication istransmitted in accordance with the particular CORESET configuration andsearch space configuration. In some aspects, the broadcast/multicastscheduling configuration identifies a mapping of unicast HARQ processidentifiers to broadcast/multicast HARQ process identifiers associatedwith the broadcast/multicast communication.

In some examples, the communication manager 704 may receive or may causethe reception component 702 to receive HARQ feedback for thebroadcast/multicast communication. In some examples, the communicationmanager 704 may transmit or may cause the transmission component 706 totransmit a retransmission of the broadcast/multicast communication. Insome aspects, the retransmission may be a broadcast/multicastretransmission or a unicast retransmission.

In some aspects, the communication manager 704 may include a set ofcomponents associated with performing operations described herein. Insome aspects, one or more components of the set of components mayinclude or may be implemented within a controller/processor, a memory, ascheduler, a communication unit, or a combination thereof, of the BSdescribed above in connection with FIG. 2. Additionally oralternatively, one or more components of the set of components may beimplemented at least in part as software stored in a memory. Forexample, a component (or a portion of a component) may be implemented asinstructions or code stored in a non-transitory computer-readable mediumand executable by a controller or a processor to perform the functionsor operations of the component.

The number and arrangement of components shown in FIG. 7 are provided asan example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 7. Furthermore, two or more components shown inFIG. 7 may be implemented within a single component, or a singlecomponent shown in FIG. 7 may be implemented as multiple, distributedcomponents. Additionally or alternatively, a set of (one or more)components shown in FIG. 7 may perform one or more functions describedas being performed by another set of components shown in FIG. 7.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, or acombination of hardware and software.

Some aspects are described herein in connection with thresholds. As usedherein, satisfying a threshold may refer to a value being greater thanthe threshold, greater than or equal to the threshold, less than thethreshold, less than or equal to the threshold, equal to the threshold,not equal to the threshold, or the like, or combinations thereof.

It will be apparent that systems or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems or methods is not limitingof the aspects. Thus, the operation and behavior of the systems ormethods were described herein without reference to specific softwarecode—it being understood that software and hardware can be designed toimplement the systems or methods based, at least in part, on thedescription herein.

Even though particular combinations of features are recited in theclaims or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims or disclosed in the specification. Although each dependent claimlisted below may directly depend on only one claim, the disclosure ofvarious aspects includes each dependent claim in combination with everyother claim in the claim set. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination withmultiples of the same element (for example, a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein is to be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (for example, related items, unrelated items, acombination of related and unrelated items, or the like, or combinationsthereof), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like, orcombinations thereof are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE), comprising: receiving downlink control information(DCI) scheduling broadcast or multicast (broadcast/multicast)communications, the DCI being scrambled by one or more radio networktemporary identifiers (RNTIs); receiving a first broadcast/multicastcommunication, of the broadcast/multicast communications, associatedwith a broadcast/multicast control channel via a physical downlinkshared channel (PDSCH) in accordance with the DCI, thebroadcast/multicast control channel being associated with a first RNTIof the one or more RNTIs; and receiving a second broadcast/multicastcommunication, of the broadcast/multicast communications, associatedwith a broadcast/multicast traffic channel via the PDSCH in accordancewith the DCI, the broadcast/multicast traffic channel being associatedwith a second RNTI of the one or more RNTIs.
 2. The method of claim 1,wherein the DCI is scrambled by a multicast RNTI for the firstbroadcast/multicast communication.
 3. The method of claim 1, wherein theDCI is scrambled by a group RNTI for the second broadcast/multicastcommunication.
 4. The method of claim 1, wherein the DCI indicates abandwidth part (BWP), and wherein the second broadcast/multicastcommunication is received in accordance with the BWP.
 5. The method ofclaim 1, wherein the DCI indicates a control resource set (CORESET)configuration and a search space configuration.
 6. The method of claim5, wherein the CORESET configuration indicates a beam configuration. 7.The method of claim 5, wherein one or more of the firstbroadcast/multicast communication or the second broadcast/multicastcommunication is received in accordance with the CORESET configurationand the search space configuration.
 8. The method of claim 1, whereinthe first RNTI corresponds to a particular beam.
 9. A method of wirelesscommunication performed by a network entity, comprising: schedulingbroadcast or multicast (broadcast/multicast) communications usingdownlink control information (DCI), the DCI being scrambled by one ormore radio network temporary identifiers (RNTIs); transmitting a firstbroadcast/multicast communication, of the broadcast/multicastcommunications, associated with a broadcast/multicast control channelvia a physical downlink shared channel (PDSCH) in accordance with theDCI, the broadcast/multicast control channel being associated with afirst RNTI of the one or more RNTIs; and transmitting a secondbroadcast/multicast communication, of the broadcast/multicastcommunications, associated with a broadcast/multicast traffic channelvia the PDSCH in accordance with the DCI, the broadcast/multicasttraffic channel being associated with a second RNTI of the one or moreRNTIs.
 10. The method of claim 9, wherein the DCI is scrambled by amulticast RNTI for the first broadcast/multicast communication.
 11. Themethod of claim 9, wherein the DCI is scrambled by a group RNTI for thesecond broadcast/multicast communication.
 12. The method of claim 9,wherein the DCI indicates a bandwidth part (BWP), and wherein the secondbroadcast/multicast communication is received in accordance with theBWP.
 13. The method of claim 9, wherein the DCI indicates a controlresource set (CORESET) configuration and a search space configuration.14. The method of claim 13, wherein the CORESET configuration indicatesa beam configuration.
 15. The method of claim 13, wherein one or more ofthe first broadcast/multicast communication or the secondbroadcast/multicast communication is transmitted in accordance with theCORESET configuration and the search space configuration.
 16. The methodof claim 9, wherein the first RNTI corresponds to a particular beam. 17.A user equipment (UE) for wireless communication, comprising: at leastone memory; and at least one processor communicatively coupled with theat least one memory, the at least one processor configured to cause theUE to: receive downlink control information (DCI) scheduling broadcastor multicast (broadcast/multicast) communications, the DCI beingscrambled by one or more radio network temporary identifiers (RNTIs);receive a first broadcast/multicast communication, of thebroadcast/multicast communications, associated with abroadcast/multicast control channel via a physical downlink sharedchannel (PDSCH) in accordance with the DCI, the broadcast/multicastcontrol channel being associated with a first RNTI of the one or moreRNTIs; and receive a second broadcast/multicast communication, of thebroadcast/multicast communications, associated with abroadcast/multicast traffic channel via the PDSCH in accordance with theDCI, the broadcast/multicast traffic channel being associated with asecond RNTI of the one or more RNTIs.
 18. The UE of claim 17, whereinthe DCI is scrambled by a multicast RNTI for the firstbroadcast/multicast communication.
 19. The UE of claim 17, wherein theDCI is scrambled by a group RNTI for the second broadcast/multicastcommunication.
 20. The UE of claim 17, wherein the DCI indicates abandwidth part (BWP), and wherein the second broadcast/multicastcommunication is received in accordance with the BWP.
 21. The UE ofclaim 17, wherein the DCI indicates a control resource set (CORESET)configuration and a search space configuration.
 22. The UE of claim 21,wherein the CORESET configuration indicates a beam configuration. 23.The UE of claim 21, wherein one or more of the first broadcast/multicastcommunication or the second broadcast/multicast communication isreceived in accordance with the CORESET configuration and the searchspace configuration.
 24. The UE of claim 17, wherein the first RNTIcorresponds to a particular beam.
 25. A network entity for wirelesscommunication, comprising: at least one memory; and at least oneprocessor communicatively coupled with the at least one memory, the atleast one processor configured to cause the network entity to: schedulebroadcast or multicast (broadcast/multicast) communications usingdownlink control information (DCI), the DCI being scrambled by one ormore radio network temporary identifiers (RNTIs); transmit a firstbroadcast/multicast communication, of the broadcast/multicastcommunications, associated with a broadcast/multicast control channelvia a physical downlink shared channel (PDSCH) in accordance with theDCI, the broadcast/multicast control channel being associated with afirst RNTI of the one or more RNTIs; and transmit a secondbroadcast/multicast communication, of the broadcast/multicastcommunications, associated with a broadcast/multicast traffic channelvia the PDSCH in accordance with the DCI, the broadcast/multicasttraffic channel being associated with a second RNTI of the one or moreRNTIs.
 26. The network entity of claim 25, wherein the DCI is scrambledby a multicast RNTI for the first broadcast/multicast communication. 27.The network entity of claim 25, wherein the DCI is scrambled by a groupRNTI for the second broadcast/multicast communication.
 28. The networkentity of claim 25, wherein the DCI indicates a bandwidth part (BWP),and wherein the second broadcast/multicast communication is received inaccordance with the BWP.
 29. The network entity of claim 25, wherein theDCI indicates a control resource set (CORESET) configuration and asearch space configuration.
 30. The network entity of claim 29, whereinthe CORESET configuration indicates a beam configuration.